blog: June 2026 security releases - #2374

✅ Deploy Preview for expressjscom-preview ready!

Name	Link
🔨 Latest commit	d1ceb49
🔍 Latest deploy log	https://app.netlify.com/projects/expressjscom-preview/deploys/6a43b4a367c0130008113d98
😎 Deploy Preview	https://deploy-preview-2374--expressjscom-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 100 (🟢 up 3 from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports
🤖 Make changes	Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

At this rate, I'm going to add an option so the date is no longer required in the filename and can instead be provided as metadata in the MDX frontmatter

At this rate, I'm going to add an option so the date is no longer required in the filename and can instead be provided as metadata in the MDX frontmatter

I think that probably removing the limit to access "future content" might solve the issue completely. Maybe we can use a MDX frontmatter field to manage visibility (isDraft?) so no need to change date anymore. As our blog posts are open source time ahead of the publication probably the visibility control makes also non-sense 🤔

Even though we no longer have the issue we had before here, you can still set the release date and it will still be visible

@ulisesgasco , it's no longer necessary to include the date in the filename. You can use frontmatter instead, just like the title, and that will be used as the post's date.